We released a patch for some smaller problems late last week, but overall the update went fairly well and there don’t seem to be any major problems caused by the big underlying changes. The changelog for the patch is at the end of this post.
There are however some rare cases on Mac and Linux where the game is running much slower than it should be for no apparent reason. We’ve contacted Unity about it since it seems to be an engine issue, so hopefully we’ll know what’s going on there soon.

GOG released a new tool that allows us to upload and release new updates by ourselves, which will speed up how fast new game versions appear on their store a lot. We’ve integrated their tool into our release pipeline so releasing updates on GOG is a single click for us now, just like on other big stores.

We’re also getting closer to getting some professional translations done, so I’ve improved our translation tools last week. We had a limitation previously where certain words would be impossible to translate into some languages - for example we have small umbrellas guests can buy from shops and the big ones available as deco that provide shade. Even though these are two very different things in English they are both called “Umbrella” but other languages use different words for each of these, so we needed to add the ability to have multiple different translations for a single English word depending on context.

Changelog (Beta 7a)

- added highlighting trash as source of bad scenery ratings in scenery rating visualization view
- added clicking on a thought marker opens the info window of the person belonging to this thought
- improved behaviour when placing a queue tile next to a ride entrance that is already connected to a path that isn’t a queue
- should fix some severe performance issues on macOS
- fixed prices in deco UI not updating when scaling deco objects using hotkeys
- fixed ride light color button being shown even if ride has no custom light colors
- fixed a case where people would sometimes not know how to get somewhere even though there’s a path
- fixed a problem with color palettes where colors would be invisible
- fixed rare case where staff couldn’t leave staff room
- fixed weirdness with wooden supports when placing rotated blueprints
- fixed edge scrolling being active while game isn’t focused
- fixed weather not getting saved/loaded properly

Art Stream

Come join us on Garrets Twitch channel on Wednesday (May 30th) at 1pm PDT to chat while watching some new Parkitect art being created.

Devlog

The multithreading stuff seems to be fairly stable right now! We will still be running a bunch of tests this week, but it looks like it will be possible to release it with Beta 7 already.
Having more guests messes with the financial balance of the game quite a bit, so we started adjusting that. As usual it will take many tiny tweaks over a longer period of time to get that feeling right again, so don’t expect that to be perfect just yet with the next update.

The audio team delivered a few hundred new sound effects, so all the props and rides that were added in the past half year or so got their sounds now!
Gordon also finished a new calm ride music track which will be very nice for the most low-intensity rides.

Garret made the existing concrete and wooden walls recolorable, which makes them a whole lot more useful:

I continued working on moving the AI code to a separate thread this week. It still needs a ton of testing, but overall work is going a bit faster than expected. The guest AI is ~95% done, pathfinding is running on its own thread as well now, and I’ve started working on moving the staff AI (which should not be too problematic overall since I can reuse most of the work done for guests).

There have been some requests for properly documented and more detailed benchmarks last time, so here’s one. These are the systems I tested on:

Low-end system:
Mac Mini 2014, Intel i5 @ 2.6GHz, integrated Intel Iris graphics
A system that’s pretty close to our minimum requirements. The main bottleneck is the lack of a proper graphics card - this system can’t even render an empty screen at 20 FPS at full resolution. Since we’re interested in the games CPU performance instead of the integrated graphics performance (and I got no other system to test with) I’ve lowered the resolution to the point where it can render an empty screen at ~55 FPS.

High-end system:
Windows 10 PC, Intel i7-6700K @ 4GHz, NVIDIA GeForce GTX 1060
A fairly recent and decent system.

I don’t have a mid-range system available for testing but it should be save to assume that performance would accordingly fall between the results from these.

All tests were run with the exact same scene and camera position in the Eastern Highlands demo park with 3.000 guests. This is a rather detailed park and that guest count is higher than it will be in the end for this park (we haven’t done a proper balancing pass yet to account for the improved performance, but something around 2.000 - 2.500 guests is probably more reasonable).

There have been some requests for “removing the guest cap” last week so I want to point out again that the game has no guest cap. If you build a park with better/more rides then there will be more guests.

The “Old” results are with the currently released Beta 6 version and the “New” results are with the upcoming multithreading version.

A fairly modest improvement of 10-15% for this specific scene. Not amazing, but nice. Worth pointing out though is that in the old version there can be some spikes occasionally where single frames take a bit longer to calculate, whereas in the new version it’s all very stable.

Improving guest performance is not only interesting for being able to have more guests in general, but also because the game allows speeding up time. Running the game at x3 speed means running the guest AI 3 times as often, so running a park with 3.000 guests at x3 speed is roughly comparable to running a park with 9.000 guests at x1 speed. This is where the performance improvements become more apparent.
Here’s the same test as above, but running at x3 speed.

The old version takes a pretty significant hit, whereas in the new version it barely has any performance impact at all.